home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group99a.txt
/
000180_icon-group-sender _Wed Sep 1 12:53:30 1999.msg
< prev
next >
Wrap
Internet Message Format
|
2000-09-20
|
2KB
Return-Path: <icon-group-sender>
Received: (from root@localhost)
by baskerville.CS.Arizona.EDU (8.9.1a/8.9.1) id MAA19536
for icon-group-addresses; Wed, 1 Sep 1999 12:52:52 -0700 (MST)
Message-Id: <199909011952.MAA19536@baskerville.CS.Arizona.EDU>
From: "Frank Lhota" <lhotaf@lexma.meitech.com>
To: "J D Burnley" <D.Burnley@sheffield.ac.uk>,
<icon-group@optima.CS.Arizona.EDU>
Subject: Re: The remove() function
Date: Wed, 1 Sep 1999 12:15:01 -0400
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Errors-To: icon-group-errors@optima.CS.Arizona.EDU
Status: RO
First of all, you should be aware that DOS has problems with deleting a file
that is currently open. Depending on how the file is opened, the version of
DOS, and whether there is any buffered data, deleting a file that is open
can succeed, fail, or result in "lost clusters". My advice is that your
program be modified to make absolutely sure that the file is closed before
remove is called. Icon cannot make any promises that the host OS cannot
keep.
My advice is that you try to come up with a small Icon program that
reproduces the problem by paring down your current program. This might
clarify the problem, and if it does not, you can post the small program to
this newsgroup for evaluation.
----- Original Message -----
From: J D Burnley <D.Burnley@sheffield.ac.uk>
To: <icon-group@optima.CS.Arizona.EDU>
Sent: Wednesday, September 01, 1999 8:55 AM
Subject: The remove() function
> I'm no programmer, although I do manage to do useful things with Icon
> which I couldn't do with any other language (esp. text manipulation).
> In most of the programs I write (using DOS), the remove() function
> refuses to delete the files named. Although of course it works from a
> stand-alone procedure devoted to the purpose, it won't work predictably
> from the same procedure called within a larger program -- even if the
> file has been explicitly closed.
>
> There may be no simple answer to this, but if there is, I'd be grateful
> to know it.
>
> Regards,
>
> David Burnley.